BlueCielo Meridian Enterprise 2012 Administrator's Guide | BlueCielo ECM Solutions

You are here: BlueCielo Meridian Enterprise Administrator's Guide > Integrating Meridian with SQL Server > Restoring a SQL Server vault to another server

Restoring a SQL Server vault to another server

A Meridian vault can be moved to another computer (for example, as a server upgrade) by restoring a backup of the vault made on the original server so long as the vault folder names and paths remain the same. This task assumes that Meridian and SQL Server are installed on the same computer. If the folder names or paths will be different, see Moving a SQL Server vault to a different folder.

Warning    It is not possible to move (by restoring from backup) a vault from a pre-Windows Server 2008 computer (including Windows XP, Windows Server 2000, or Windows Server 2003) to a post-Windows Server 2008 (including Windows Vista) or later computer without adverse side effects. The possible side effects include folders and documents not being accessible, and vault corruption. The cause is Windows API functions that behave differently between pre-Windows Server 2008 and post-Windows Server 2008 operating systems.

The only supported method to move an existing vault from a pre-Windows Server 2008 computer to a post-Windows Server 2008 computer is by importing it from the source server into a new vault on the post-Windows Server 2008 computer.

To restore a SQL Server vault to the same location on another server:

  1. On the original server, export to a file the registry information located at the following registry key:
HKEY_LOCAL_MACHINE\Software\Cyco\AutoManager Meridian\
CurrentVersion\Installed Datastores\<VaultName>

Where <VaultName> is the name of the vault to be restored.

  1. Edit the resulting .REG file in any text editor and change the three paths under CompoundItemService (DataPath, IndexPath, and LogPath) to point to the new location (and perhaps also the stream files location specified by the <VaultName>\StreamService\RootPath registry value).
  2. On the new server, restore the database with the SQL Enterprise Manager to the new location, making sure that the database name is the same as what is specified in the .REG file for <VaultName>.
  3. Import the .REG file editing in step 2 to the new server.
  4. Restart the AutoManager EDM Server service.
  5. Repeat this procedure for each vault to be restored.

Related concepts

Integrating Meridian with SQL Server

Understanding how Meridian works with SQL Server

Understanding SQLIO

Understanding vault cache memory

Understanding SQL Server vault backups

Related tasks

Integrating with a separate SQL Server computer

Configuring the Windows account used by Meridian

Creating a SQL Server account for use by Meridian

Configuring the SQL Server account used by Meridian

Migrating a Hypertrieve vault to SQL Server

Moving a SQL Server vault to a different folder

Monitoring SQL Server vault performance

Minimizing SQL Server log file size


Copyright © 2000-2012 BlueCielo ECM Solutions

www.bluecieloecm.com